|
Data Collection Using a PLC
Unit
-
PLC data is collected in a PLC Unit with
superior environmental resistance without using a computer.
-
Until now, data has been collected in PLC
memory. Using an SPU Unit, however, eliminates the need for a PLC
with a large-capacity memory and also eliminates the need for programming
data collection in the ladder program.
|
CS1W-SPU01/02-V2
|
CJ1W-SPU01-V2
|
|
Fast Collection of Large Amounts of
Data with Data Concurrency
-
Direct use of the PLC bus instead of
communications via a serial connection or LAN enables large amounts of
data to be collected at a high speed.
-
Some data collection devices from other
companies may not provide data concurrency. The SPU Unit, however,
provides concurrency of simultaneous data.
No Ladder Programming
-
No ladder programming is required for data
collection. Data can be collected simply by performing the settings from
the setting software (i.e., SPU-Console).
-
No need to leave extra space in the PLC
memory for saving data.
Note: The PLC cycle time increases in
proportion to the number of points collected.
Restriction-free Data Configuration
Files without Depending on PLC Memory Space
-
Files can be created with the desired data
configuration for only the necessary data from PLC memory.
-
The data to be collected can be stored in
files in the required data type, such as BOOL, REAL, INT, BCD, or
STRING.
-
Data configuration files required for the
host computer can be created, so necessary data can be retrieved even if
the SPU is mount in a device after the PLC is already set up.
-
CHANNEL_BLOCK has been added to the
variable data types from SPU Unit version 2.0. When the data type
is set to CHANNEL_BLOCK, the data in a consecutive memory area starting
from the specified address for the specified number of elements is
handled as a single data item with no commas.
Recipe Function
-
The recipe function enables writing
numeric data (such as production parameters) and text strings to a memory
area of the PLC. Using the recipe-writing function simplifies tasks such
as retooling.
(Note: The recipe function can be used only in Data Storage Mode.)
* Numeric data and text strings to be
written to a memory area of the PLC must
be created in advance as recipe data (i.e., a CSV file) and stored in a
Memory Card in the SPU Unit.
-
Ladder programming for developing recipe
data is not required.
-
Using the recipe function saves PLC memory
by saving recipe data to a Memory Card in the SPU Unit rather than
requiring saving to the PLC data memory.
-
Recipe data can be written in response to
a request from the PLC or from a computer or other external device.
-
Numeric data and text strings can be changed even when the SPU Unit
is operating.
Data Connectivity with the
Computer
-
The collected data can be loaded onto a
computer via a PC card or Ethernet.
-
Data can be loaded onto the host computer
with simple settings by using the Data Management Middleware software.
-
Using shared folders, data files collected
in the SPU Unit can be accessed from a LAN-connected Windows
computer just as if accessing files on the computer itself.
Collection Methods to Match
the Application
Depending on the application, the Data
Storage Mode can be used to collect data at a specific time or when there
is a change in data, and the Sampling Mode can be used to accurately
collect data at high speed. The Data Storage Mode enables establishing a
system for error monitoring and production management for each lot or
value by recording snapshots of data during production and when errors
occur.
Note: The Sampling Mode and Data Storage
Mode cannot be used at the same time.
Sampling Mode
(Previous Function)
In this mode, I/O memory data for the PLC is sampled at a constant time
interval. Data can be faithfully reproduced from the collected data.
Data Storage Mode
In this mode, the specified PLC I/O memory can be recorded when triggered
by a specific event. The mode can be used to record data when a specified
bit turns ON or at a specified time. Data can also continue being recorded
at a constant time interval after an event occurs. This enables
establishing a system for error monitoring and production management for
each lot and value by recording snapshots of data during production or
when errors occur.
Note: The time interval is less
precise than the interval in Sampling Mode.
Event-triggered Collection
Patterns
The patterns include memory events, which
occur when a memory value matches a specified condition, and scheduled
events, which occur at a specified time or time
interval. The occurrence of these events can be used to implement rules,
such as those for starting and stopping data collection. (Applicable only
in Data Storage Mode.)
Memory Events
-
Memory events can be set to generate an event when a change occurs in I/O
data in PLC memory. Using memory events, events can be generated for a
change in a bit
ON/OFF status or by comparison to a set value (i.e., equal, above, below,
or within range). For example, data could be collected only once when bit
A turns ON. Alternatively, an event rule could be defined to start
collection when bit A turns ON and stop collection when bit B turns ON.
Scheduled Events
-
Scheduled events can be set to generate an
event at a specific date and time using Scheduler settings.
-
Event rules can be defined with Scheduler settings for collecting data as
a result of events specified, for example, by the hour (e.g., every hour),
day (e.g., every day), or week (e.g., every Monday). It is also possible
to specify events by operating days or for the end of the month.
Collection Settings
Changeable during PLC Operation
-
Collection settings can be changed and
collection can be restarted without turning OFF the PLC.
-
Required data can be added and the
collection interval can be changed even while the system is operating.
Installing an SPU enables adding various systems after the system is
already in operation.
Note: The PLC cycle time increases in
proportion to the number of points collected.
|
These functions enable the
following applications simply by making settings. |
The movement end position
and filling pressure are recorded for each workpiece at events generated
for starting and stopping filling.
Process data for each
wafer can be recorded from receiving the wafer until completion.
During the testing, process data can be recorded for each product from the
start of tests until completion.
Setting Software That Is
Easier To Use than Ever Before
-
Project Explorer
SPU Unit connection destinations can be managed using the SPU-Console.
SPU Unit settings can be saved as projects, edited, and managed.
For example, a project that has been previously set can be copied and
easily reused.
-
Data Collection
Status Display and Error Log Display
The SPU Unit's operating status and error information can be
displayed on the SPU-Console. A list can be displayed showing the status
of data being collected, current errors, or error log. For example, the
total time required to collect data and the total size of data
collection files can be displayed.
-
Importing and
Exporting Variable Definitions Using CSV Files
All variable definitions can be exported to CSV files. Variable
definitions can then be edited using software such as spreadsheets.
Also, data on units and scaling, for example, can be batch-edited using
a spreadsheet and imported to the SPU-Console.
-
Unit Setup Using
the CX-programmer
Unit setup for SPU Unit version 2.0 can be performed from CX-One
version 2.1 (scheduled to be released this summer). IP addresses can be
set from the CX-Programmer.
|
Sitemap
